Computer telephony integration with connection of the computer via a presence server

ABSTRACT

Clients in a data network can subscribe to CTI Services and in this regard must be reachable by the CSTA gateway (CCGW). If this is not the case, because for example an error occurs in the data network, then the transmission of unnecessary messages can be prevented or stopped. The clients can be connected via a server to the CCGW, where the server monitors the status of the clients and acknowledges the messages addressed to an unreachable client with error messages. The server is preferably an XMPP server and the clients are preferably XMPP clients. In order to permit transport of the CSTA messages via XMPP, info/query stanzas according to RFC 3920 can be used, since they have the advantage over message stanzas that they can be acknowledged by a remote station.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is the United States national phase of 35 USC §371 ofPCT International Application No. PCT/EP2011/006531, filed on Dec. 22,2011, and claiming priority to EP 11 007 818.5 filed on Sep. 26, 2011,and EP 10 016 049.8, filed on Dec. 23, 2010.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Embodiments of the invention relate to methods for monitoring of aconnection in an exchange system in a telecommunications network

2. Background of the Related Art

Data networks are primarily used for networking computers, for example,PCs with servers. Methods and arrangements in which applicationsinstalled on computers control and monitor communication systems andcommunication connections are generally known as CTI solutions(CTI=Computer Telephony Integration). Both communication system portsand connections between ports can be controlled and monitored in thismanner. The respective connections are temporary communication channelsbetween two or more participants of one or more communication systems.

When a CTI solution is operating, data with control and statusinformation is transmitted each time between a communication system anda CTI application (CTI application program). For this purpose, thecommunication systems provide special interfaces for exchanging data,the CTI interfaces. Likewise, the applications and/or PCs provide acorresponding CTI interface for this data exchange. For this, the CTIinterfaces of the communication system and those of the application areconnected with one another via a data line or a data network. Themaximum number of CTI interfaces is limited on one communication systemso often a telephony server is connected between the communicationsystem and the applications.

The publication WO 98/51092 AI “Computer Telephony Integration Gateway”shows a public communication network with several communication systemsand a private communication network with several domains that eachfeature computers with applications for controlling and/or monitoring ofthe public communication network's resources. The arrangement shownfeatures a “CTI gateway” as a conversion device, which changes the typeof data sent for controlling and/or monitoring of resources from thepublic communication network to the private communication network, sothat this data appears as the data from one single public communicationnetwork, and conversely changes the data that is sent by the privatecommunication network with the applications to the public communicationnetwork, as though it had been sent from a private communication networkwith only one application.

DE 000010159636 B4 describes a method for controlling and/or monitoringof resources and connections by means of exchanging data betweencommunication systems and at least one application, wherein the datahave identifiers that differentiate the resources and the connectionsand the identifiers of the resources are converted during the exchangein such a way that they present themselves as the identifier of onesingle communication system with subscriber connections for the one orevery application, characterized in that each of the identifiers of theconnection between resources of different communication systemscomprises one local connection number (call ID) of the communicationsystem participating in the connection and one global connection number(call ID) and in that the global connection number (call ID) istransmitted for the application through the conversion so that it is notdistinguishable from a local connection number (call ID) by theapplication.

BRIEF SUMMARY OF THE INVENTION

The invention concerns a method for automatic monitoring of a connection(CTI-L) in an exchange system (PBX) in a telecommunications network (TN)with a data network (DN) in which an exchange system (PBX) of thetelecommunications network is connected with an IM server (XS) of thedata network via a device (CCGW), which enables the IM server to providethe computer telephony integration services of the exchange system (PBX)to a communication participant on the data network.

According to embodiments of the invention, a method is provided forautomatic monitoring of a connection (CTI-L) in an exchange system (PBX)in a telecommunications network (TN) with a data network (DN) in whichan exchange system (PBX) of the telecommunications network is connectedwith an IM server (XS) of the data network via a device (CCGW), whichenables the IM server to provide the computer telephony integrationservices of the exchange system (PBX) to a communication participant onthe data network. Computer telephony integration services and messagesare transmitted by a request/response mechanism that provides an errormessage to the sender in the event of a failure.

One preferred embodiment of the present invention, whose features canalso be combined with features of other embodiments, provides a methodfor using IQ stanzas for the request/response mechanism.

One preferred embodiment of the present invention, whose features canalso be combined with features of other embodiments, provides a methodfor using “direct presence” messages for the request/response mechanism.

One preferred embodiment of the present invention, whose features canalso be combined with features of other embodiments, provides a methodwhich enables the IM server to provide computer telephony integrationservices of the exchange system (PBX) to a communication participant onthe data network, in which an IM client (XC) is allowed to subscribe tosuch computer telephony integration services of the exchange system(PBX).

Another preferred embodiment of the present invention, whose featurescan also be combined with features of other embodiments, provides amethod in which the device (CCGW) performs mapping between aCSTA-specific Invoke ID (CSTA-IID) on one side and a Jabber Identifier(JID) of the IM client and/or an XMPP session ID (XSID).

Another preferred embodiment of the present invention, whose featurescan also be combined with features of other embodiments, provides amethod in which the communication between the device (CCGW) and the IMserver is configured as a server-server connection.

Another preferred embodiment of the present invention, whose featurescan also be combined with features of other embodiments, provides amethod in which the communication between the device (CCGW) and the IMserver is executed via a server component according to XEP 0114 oranother Jabber component protocol comparable to XEP 0114.

Another preferred embodiment of the present invention, whose featurescan also be combined with features of other embodiments, provides amethod in which the so-called Invoke ID is used for assigning a requestto an associated response.

Another preferred embodiment of the present invention, whose featurescan also be combined with features of other embodiments, provides amethod in which the Invoke ID used for assigning a request to anassociated response is unique across all requests.

Another preferred embodiment of the present invention, whose featurescan also be combined with features of other embodiments, provides amethod in which the IQ stanzas are used for CSTA transport via XMPP,said IQ stanzas featuring a request/response mechanism that iscomparable to that request/response mechanism used by CSTA.

Another preferred embodiment of the present invention, whose featurescan also be combined with features of other embodiments, provides amethod by which an IM client generates an XMPP session ID, which isdifferent from other XMPP session IDs for the same IM client.

Embodiments are described below in more detail based on preferredexemplary embodiments and with reference to the figures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 schematically shows a first arrangement of system components forrealization of an exemplary embodiment of one method according to theinvention;

FIG. 2 schematically shows a second arrangement of system components forrealization of an exemplary embodiment of one method according to theinvention;

FIG. 3 schematically shows a flow diagram of a component of a sequenceof one method according to the invention based on a preferred exemplaryembodiment of the invention;

FIG. 4 schematically shows a flow diagram of a component of a sequenceof one method according to the invention based on a preferred exemplaryembodiment of the invention;

FIG. 5 schematically shows a flow diagram of a component of a sequenceof one method according to the invention based on a preferred exemplaryembodiment of the invention;

FIG. 6 schematically shows a flow diagram of a component of a sequenceof one method according to the invention based on a preferred exemplaryembodiment of the invention;

FIG. 7 schematically shows a flow diagram of a component of a sequenceof one method according to the invention based on a preferred exemplaryembodiment of the invention;

FIG. 8 schematically shows a flow diagram of a component of a sequenceof one method according to the invention based on a preferred exemplaryembodiment of the invention;

FIG. 9 schematically shows a flow diagram of a component of a sequenceof one method according to the invention based on a preferred exemplaryembodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIGS. 1 and 2 schematically show the embedding of the CCGW in the entiresystem. FIG. 2 shows in particular an embedding of the CCGW in theentire system.

As shown in FIG. 1, functions of a telecommunications network TN in adata network DN, consisting of telecommunications terminals T1, T2, T3,T4 and an exchange system PBX and, if applicable, additional componentsare integrated by integrated by connecting an exchange system PBX of thetelecommunications network to an IM server XS on the data network, wherethe clients C1, C2, C3 and C4 communicate via the IM server XS, via thedevice CCGW, which enables the IM server to provide computer telephonyintegration services of the exchange system PBX to a communicationparticipant on the data network.

On the one side, the connection to the feature processing FP isestablished via CSTA XML here by means of a so-called CSTA serviceprovider (CSP). On the other side, the CSTA is transmitted via XMPP tothe XMPP server XS. Using the CCGW, an XMPP client S1, S2 can subscribeto CTI services. Communication between the CCGW and the XMPP server canbe arranged as a server-server or server-client connection as well asvia a server component according to XEP 0114 or another Jabber componentprotocol comparable to XEP 0114.

The IM server XS also creates a connection between clients S1, S2 andthe Internet IN in the example shown in FIG. 2. VI indicates avisualization of the communication on the terminal T1.

The XMPP protocol can serve as a typical example of an instant messaging(IM) protocol. XMPP-based client/server architectures run asynchronousto the telephone in the prior art. Automatic monitoring of a CTI linkwithin an XMPP environment is not provided according to the prior art.

According to the exemplary embodiment of the invention considered, theXMPP client subscribes to CTI services via the XMPP server with anexchange system PBX. The exchange system “PBX” provides this functionthrough a Call Control Gateway (CCGW). The CCGW provides a gateway fromthe PBX to the XMPP network and is the connection between the CTI of aPBX and the XMPP server. The CTI services themselves—depending on theembodiment of the invention, for example, CSTA events and CSTArequests—are exchanged then via the XMPP network as XMPP IQ messages(so-called IQ stanzas) preferably according to RFC 3920bis.

The PBX and XMPP server (XS) are connected using a Call Control Gateway(CCGW). Through this call control gateway, an XMPP client can subscribeto and provide CTI services. This concerns the CSTA call controlservices and events described in ECMA-269 in one embodiment.

FIG. 2 schematically shows the embedding of the CCGW in the entiresystem realized in the form of OpenScape Office MX and the associatedaffected components. On one side, the connection to feature processingis established via CSTA XML. On the other side, CSTA is transmitted viaXMPP to the XMPP server (in the exemplary embodiment shown in FIG. 2:Openfire). Using the CCGW, an XMPP client S1, S2 (Spark for example) cansubscribe to CTI services. To enable the transport of XML-encoded CSTAvia XMPP, IQ stanzas are expanded by a <csta/> tag. IQ stanzas arepreferred for transporting CSTA, because they offer the advantage overmessage stanzas that they are acknowledged by the other side.

Communication between the CCGW and the XMPP server can be realized indifferent ways depending on the embodiment of the invention:

-   a) via an XMPP server-server connection, i.e. the CCGW acts as an    autonomous XMPP server.-   b) via an XMPP client-server connection or another Jabber component    protocol comparable to XEP 0114, i.e. the CCGW is administered as    the client in the XMPP server (e.g. Openfire).-   c) as a server component according to XEP 0114 or another Jabber    component protocol comparable to XEP 0114, i.e. the CCGW is a server    component of the XMPP server.

FIG. 3 shows an exemplary embodiment of the invention using a CSTAMakeCall with MakeCall Response and an event including anacknowledgment. Client C sends the message 11 with the text 11 to theserver S. The server S answers by sending the message 12 with the text12 to the client C. The server S then sends message 13 with text 13 tothe client C, whereupon the client C sends message 14 with text 14 tothe server S.

The texts of the messages are compiled in an overview at the end of thedescription. By transmitting CTI services and messages as IQ stanzasbetween the CCGW and the XMPP client (via XMPP server), an automaticmonitoring of the CTI link from the XMPP client to its XMPP server isalso ensured. Namely, if this connection is no longer present (e.g. dueto a faulty LAN segment), the XMPP server must respond in place of theaddressed XMPP client to an IQ stanza request with an “error” type IQstanza with the value “service unavailable” (RFC 3920bis). In the eventof error, appropriate measures for clearing the error can thereby beinitiated at the CCGW on the CTI level.

FIG. 4 shows an exemplary embodiment of the invention using an IQ stanzaerror. The device CCGW sends a message 21 with the text 21 to the serverXS, whereupon the server XS sends the message 22 with the text 22 to thedevice CCGW. The texts of the messages are compiled in an overview atthe end of the description.

In the event of an unexpected disconnection, the arriving messages arenot saved in the CCGW and are transmitted by the CCGW during the nextlogin of the corresponding user. That is to say if this user has set amonitoring point on a device, then the unidirectional CSTA events areforwarded to the user. These events are only relevant for a limitedperiod however. If the user logs into the XMPP server hours or even daysafter the last disconnection, then it is completely irrelevant whichevents occurred in the user's absence. Rather, the sender of the CSTAevents (i.e. the CCGW) can cancel the monitoring point by receiving theerror type IQ stanza and therefore stop sending additional, unnecessaryXMPP messages. Another option for starting and/or stopping transmissionof CTI services and messages using IQ stanzas between CCGW and XMPPclients (via XMPP server) is the use of “directed presence” messages(RFC 3921bis). In this case, the XMPP client sends its presence status(for example in the form: unavailable) directly to the CCGW. The CCGWrecognizes the online status of the XMPP client and can respondaccordingly. The use of the directed presence mechanism furthermore hasthe added advantage that the CCGW does not have to be located in theroster (contact list) of the user to get presence messages, and thus theuser always sees only his contact list with “real” users.

The behavior of an XMPP server in response to the receipt of differentmessage types is defined for different cases within the RFC 3921bis. Thedescribed cases, for example, include that the Jabber ID does not exist,or that the JID exists, but is not available via the addressed resource.The configurations of this RFC administer XMPP servers upon receipt ofan IQ message, that either is not addressed directly to a resource or ifthe addressed resource is not available, in that the server respondswith the <service unavailable/> error type. In this case, an error onthe IQ stanza request of the CSTA event type could automatically stop orpause the CSTA monitoring point.

So-called XMPP direct presence messages (RFC 3921bis) can also be usedin order to inform the device CCGW about the online status of itsclients, even if the CCGW is not found in the user roster. To achievethis, the client would have to address a presence message directly tothe CCGW If the XMPP client server switches off the XMPP client serverin a controlled fashion (i.e. the user closes the XMPP clientapplication), the client application sends an “unavailable” type ofpresence stanza to its XMPP server. According to RFC 3921bis, thispresence stanza must also be sent by the XMPP server to the XMPPterminals that were previously provided by the client application withdirect presence messages (i.e. also to the CCGW). The CCGW can then stopthe CSTA monitoring point in the CCGW. Because the XMPP server monitorsthe XMPP connection to its XMPP clients, the XMPP server also noticeswhether the connection to an XMPP client was lost in an uncontrolledmanner (e.g. by failure of the corresponding LAN segment). This XMPPclient is now no longer reachable, so it receives the status“unavailable”. The XMPP server must also independently inform any XMPPentities that previously only received “directed presence” stanzas fromthis client with an “unavailable” type presence stanza (thus, also theCCGW) (see RFC 3921 bis).

In both cases (i.e. in controlled and uncontrolled interruptions of theXMPP client-server connection), the “directed presence” functionalityaccording to RFC 3921bis can therefore automatically be used to stop orpause the CSTA monitoring point in the CCGW.

The cited documents can be retrieved on the Internet at the website ofthe International Engineering Task Force. It is assumed here that3920bis19 and 3921bis17 replace the existing RFC 3920 and RFC 3921.

FIGS. 5 to 9 show further exemplary embodiments of the invention inwhich the connection between the CCGW and XMPP server is realized as aclient-server connection. The CCGW device in these cases is preferablylikewise administered as an XMPP client on the XMPP server. FIG. 5 showsthe transmission of CSTA services and events. The client C is preferablyan XMPP client, the server S is an XMPP server that takes on a purelypassive role as a router. The client C sends a message 31 with the text31 to the server XS, whereupon the server XS sends a message 32 with thetext 32 to the device CCGW. The device CCGW now sends a message 33 withthe text 33 to the server XS, whereupon the server sends a message 34with the text 34 to the client. Afterwards, the device CCGW sends amessage 35 with the text 35 to the server, whereupon the server sends amessage 36 with the text 36 to the client C. Afterwards, the client Csends a message 37 with the text 37 to the server, whereupon the serversends a message 38 with the text 38 to the device CCGW.

FIG. 6 shows the behavior when the client is not available. The deviceCCGW sends a message 41 with the text 41 to the server XS, whereupon theserver XS sends a message 43 with the text 43 to the device CCGW.Sending of a message 42 by the server to the client C does not happenhere. The XMPP server takes on an active role here because no“end-to-end” connection exists (any longer).

FIG. 7 shows a further exemplary embodiment of the invention based onthe use of direct presence messages. Here, the XMPP client has theaddress test@example.com/test, the server S is an XMPP server, and thedevice CCGW is set up as an XMPP client with the addressccgw@example.com/ccgw. The client C sends a message 51 with the text 51and subsequently a message 52 with the text 52 to the server. Thereuponthe server sends a message 53 with the text 53 to the device CCGW. Theclient C sends a message 54 with the text 54 and subsequently a message55 with the text 55 to the server. Thereupon the server sends a message56 with the text 56 to the device CCGW. Afterwards, the client C sends amessage 57 with the text 57 to the server. In this example, the XMPPclient sends the direct presence status to the device CCGW for logon andlogoff.

In the exemplary embodiment shown in FIG. 8, the XMPP client C has theaddress test@example.com/test, the server S is an XMPP server, and thedevice CCGW is set up as an XMPP client with the addressccgwgexample.com/ccgw. Upon a logoff without direct presence status bythe client, the server assumes this task. The client C sends a message61 with the text 61 and a message 62 with the text 62 to the server,whereupon the server sends a message 63 with the text 63 to the deviceCCGW. The client C then sends a message 64 with the text 64 and amessage 65 with the text 65 to the server, whereupon the server sends amessage 63 with the text 66 to the device CCGW.

In the exemplary embodiment in FIG. 9, the XMPP client C has the addresstest@example.com/test, the server S is an XMPP server, and the deviceCCGW is set up as an XMPP client with the address ccgw@example.com/ccgw.For connection interruptions between the client and server, the servermust send the direct presence status. The client C sends a message 71with the text 71 and a message 72 with the text 72 to the server,whereupon the server sends a message 73 with the text 73 to the deviceCCGW. The client C then sends a message 74 with the text 74 to theserver, whereupon the server sends a message 76 with the text 76 to thedevice CCGW. Sending of the message 75 by the client C to the server Sdoes not happen in this case.

Below is a list of the message texts used in the description that is anexpress component of the present description.

Text 11: <iq from=“test@example .com/test ” to=“ccgw@example. com/ccgw”xml :lang=“en” id=“123456” type=“set”> <csta xmlns=“csta” version=“ 1.0” encoding=“UTF-8 ”> <MakeCall xmlns=“http ://www.ecma- ... Text 12:<iq from=“ccgw@example. com/ccgw” to=“ test@example. com/test ” xm1:lang=“en” id=“123456” type=“result ”> <csta xmlns=“csta” version=“1 .0”encoding=“UTF-8 ”> <MakeCallResponse xmlns=“http: //www.ecma-... Text13: <iq from=“ccgw@example .com/ccgw” to=“test@example .com/test ” xml:lang=“en” id=“234567” type=“set”> <csta xmlns=“csta” version=“1 .0”encoding=“UTF-8 ”> <ServiceInitiatedEvent xmlns=“http ://www.ecma- Text14: <iq from=“test@example. com/test ” to=“ccgw@example. com/ccgw” xml:lang=“en” id=“234567” type=“result ” /> Text 21: <iqto=“seb@wit0234c/sebl” type=“set” from=“ccgw@wit0234c/ccgw”xmlns=“jabber: client” id=“as234sf d”> <csta xmlns=“csta” version=“1 .0”encoding=“UTF-8 ”> <EstablishedEvent xmlns :csta=“http ://www. ecma- ...... </EstablishedEvent> </esta> </iq> Text 22: <iqfrom=“seb@wit0234c/sebl” to=“ccgw@wit0234c/ccgw” type=“error”id=“as234sfd”> <csta xmlns=“csta” version=“1 .0” encoding=“UTF-8”><EstablishedEvent xmlns :csta=“http ://www. ecma- ... ... </csta> <errorcode=“503” type=“cancel ”> <service-unavailable xmlns=“urn :iet f:params :xml :ns :xmppstanzas” /> </error> </iq> Text 31: <iqfrom=“test@example . com/test” to=“ccgw@example . com/ccgw” id=“123456”type-“set” > <csta xmlns=“csta” version=“1 .o” encoding=“UTF- 8” ><MakeCall xmlns=“http ://www . ecma- ... Text 32: <iq from=“test@example.com/test” to=“ccgw@example .com/ccgw” id=“123456” type=“set” > <cstaxmlns-“csta” version-“I .0” encoding-“UTF- 8” > <MakeCall xmlns-“http://www .ecma- ... Text 33: <iq from=“ccgw@example .com/ccgw”to=“test@example .com/test” id=“123456” type=“result ” > <cstaxmlns=“csta” version=“1 .o” encoding=“UTF- 8” > <MakeCallResponse xmlns-“http ://www .ecma- ... Text 34: <iq from=“ccgw@example .com/ccgw”to=“test@example .com/test ” id=“123456” type=“result ” > <cstaxmlns=“csta” version=“1 .0” encoding=“UTF- 8” > <MakeCallResponse xmlns-“http ://www. ecma- ... Text 35: <iq from=“ccgw@example .com/ccgw”to=“test@example .com/test” id-“234567” type-“set” > <csta xmlns=“csta”version=“1 .0” encoding=“UTF 8” > OervicelnitiatedEvent     xmlns=“ http: //www . ecma- ... Text 36: <iq from=“ccgw@example .com/ccgw”to=“test@example .com/test ” id=“234567” type=“set” > <csta xmlns=“csta”version=“ 1 .0” encoding= “UTF- 8” > <ServiceInitiatedEvent xmlns=“ http: //www . ecma- ... Text 37: <iq from-“test@example .com/test”to-“ccgw@example . com/ccgw” id=“234567” type=“result ” / > Text 38: <iqfrom-“test@example .com/test” to-“ccgw@example .com/ccgw” id=“234567”type=“result ” / > Text 41 = Text 35 Text 43: <iq from= “test@example.com/test” to= “ccgw@example . com/ccgw” id= “234567” type= “error” ><csta xmlns= “csta” version=“1 .0” encoding=“UTF- 8” ><ServiceInitiatedEvent xmlns= “http://www.ecma- .. </csta> <error code=“503” type= “cancel” > <service- unavailable xmlns= “urn : ietf : params: xml :. .. ”/> </error> </iq> Text 51: <presence/> Text 52: <presenceto= “ccgw@example .com/ccgw” /> Text 53: <presence from= “test@example.com/test” to= “ccgw@example .com/ccgw” /> Text 54: <presence><show>away</ show> <status>gone fishing</status> </presence> Text 55:<presence to= “ccgwgexample .com/ccgw” type= “unavailable” /> Text 56:<presence from= “test@example .com/test” to= “ccgw@example .com/ccgw”type= “unavailable” / > Text 57: <presence type= “unavailable” / > Text61 = Text 51 = Text 71 Text 62 = Text 52 = Text 72 Text 63 = text 53 =Text 73 Text 64 = Text 54 = Text 74 Text 65 = Text 57 Text 66 = Text 56= Text 76

The invention is not limited to the exemplary embodiments as described;the person skilled in the art can discover further exemplary embodimentsof the invention based on the description given here.

1-12. (canceled)
 13. A communication system comprising: an exchangesystem; an instant messaging (IM) server; a call control gatewayconnected between the IM server and the exchange system so that the IMserver is communicatively connected to the exchange system, the callcontrol gateway configured to enable the IM server to provide computertelephony integration (CTI) services of the exchange system to at leastone client connected to the IM server; a plurality of clients comprisinga first client and a second client, the clients connected to the IMserver such that the first client is communicatively connectable to thesecond client; and the first client being configured to exchangemessages with the call control gateway relating to the CTI services viathe IM server so that a CTI link about which the CTI services areprovided to the first client is monitored by the call control gateway.14. The system of claim 13, comprising: a plurality of terminalscomprising a first terminal and a second terminal, the terminalsconnected to the exchange system such that the first terminal iscommunicatively connectable to the second terminal.
 15. The system ofclaim 13, wherein the IM server is configured to monitor a connectionbetween the IM server and the first client to determine when the firstclient is unavailable, the IM server configured to send a presencemessage to the call control gateway in response to determining that thefirst client is unavailable to cause the call control gateway to stopmonitoring the CTI link.
 16. The system of claim 13, wherein the firstclient is configured to send a presence message to the call controlgateway to identify an unavailable presence of the first client forfuture use of the CTI services to effect a stopping of the monitoring ofthe CTI link by the call control gateway.
 17. The system of claim 13,wherein the IM server is configured to determine when the first clientis no longer connected to the IM server and sends a presence message tothe call control gateway upon a determination that the first client isno longer connected to the IM server, the call control gatewayconfigured to stop the monitoring of the CTI link in response to thepresence message received from the IM server.
 18. The system of claim13, wherein for each of the messages exchanged between the first clientand the call control gateway, text of previously exchanged messages arecompiled in an overview at an end of a description of the message. 19.The system of claim 13, wherein the messages exchanged between the firstclient and the call control gateway are comprised of Info/Query (IQ)stanzas.
 20. The system of claim 19, wherein the IM server is configuredto determine when the first client is no longer connected to the IMserver and sends an error type IQ stanza to the call control gateway inresponse to determining that the first client is no longer connected tothe IM server.
 21. The system of claim 13, wherein the IM servercomprises non-transitory memory and at least one processor.
 22. Thesystem of claim 13, wherein the IM server is configured so that the IMserver transmits messages that are directed for use of the CTI servicesby the first client to the call control gateway, each of these messageshaving an end of a description that provides information relating to theCTI services to enable the call control gateway to monitor the CTI linkabout which the CTI services are provided to the first client via the IMserver.
 23. The system of claim 13, wherein the IM server is configuredto send an error message to the call control gateway in response to afailure of the CTI link.
 24. The system of claim 13, wherein the firstclient is an Extensible Messaging and Presence Protocol (XMPP) client,and wherein the call control gateway is configured to perform mappingbetween a Computer Supported Telecommunications Applications (CSTA)specific Invoke ID on one side and a Jabber identifier of at least oneof the first client and an XMPP session ID on the other side.
 25. Thesystem of claim 13, wherein communications relating to the CTI link thatare exchanged between the call control gateway and the IM server isrealized via a member of the group consisting of a server componentaccording to XEP 0114 and a Jabber component protocol comparable to XEP0114.
 26. The system of claim 13, wherein Computer SupportedTelecommunications Applications (CSTA) information is transportedbetween the call control gateway and the first client via ExtensibleMessaging and Presence Protocol (XMPP) with Info/Query (IQ) stanzas. 27.The system of claim 13, wherein the first client is configured togenerate an Extensible Messaging and Presence Protocol (XMPP) session IDthat is different from any other XMPP session IDs for the first client.28. A method for automatic monitoring of a connection of an exchangesystem in a telecommunications network with a data network, wherein anexchange system of the telecommunications network is connected with aninstant messaging (IM) server of the data network via a device that isconfigured to enable the IM server to provide computer telephonyintegration services of the exchange system to a communicationparticipant on the data network, the method comprising: transmittingcomputer telephony integration (CTI) services via the IM server using arequest/response mechanism; transmitting messages associated with use ofthe CTI services between the device and a client of the IM server viathe IM server; compiling text of the messages transmitted between thedevice and the client at an end of a description of a message to be sentto the device, the compiled text providing information relating to theCTI services, the message configured to be sent to the device to enablethe device to monitor a CTI link about which the CTI services areprovided to the client via the IM server; and providing an error messageto the device in response to a failure of the CTI link using therequest/response mechanism.
 29. The method of claim 28, wherein therequest/response mechanism is an Info/Query (IQ) stanza mechanism. 30.The method of claim 28, wherein the request/response mechanism is adirect presence message.
 31. The method of claim 28, comprisingrealizing the communication between the device and the IM server as aserver-server connection.
 32. The method of claim 28, comprisingrealizing the communication between the device and the IM server as aserver-client connection.